@jarrodek @alexpmule Thank you very much for the PR but I am still seeing the same issue.

Error: Expected OAS but could not find version header.
at ApiSearch._readApiType (/Users/sukanya/api-console/demo/demo-server/api/amf-service/api-search.js:138:15)
at async AmfService.parse (/Users/sukanya/api-console/demo/demo-server/api/amf-service/amf-service.js:219:20)
at async ApiParser.processBuffer (/Users/sukanya/api-console/demo/demo-server/api/api-parser.js:65:19)
at async ApiParser.parseFile (/Users/sukanya/api-console/demo/demo-server/api/api-parser.js:8:18)
at async apiRequest (/Users/sukanya/api-console/demo/demo-server/api.js:17:14)
at async demoApi (/Users/sukanya/api-console/demo/demo-server/api.js:41:5)
at async /Users/sukanya/api-console/node_modules/koa-compress/index.js:43:5
TypeError: Cannot read properties of undefined (reading '0')
at ApiParser._bufferIsZip (/Users/sukanya/api-console/demo/demo-server/api/api-parser.js:81:18)
at ApiParser.processBuffer (/Users/sukanya/api-console/demo/demo-server/api/api-parser.js:40:14)
at ApiParser.parseFile (/Users/sukanya/api-console/demo/demo-server/api/api-parser.js:8:29)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

I added more chances to support OAS 3 in the demo page. @rsukanya1013 please mind that this is a part of a demo page used for internal development and it is not production quality code. Please, do not use in production. You can take a look and understand the logic, but you should consider writing your own AMF parser instance. The demo parser service was never tested or intended for production environment.

Sure thank you very much for your help here @jarrodek .